Linked.Archi LeanIX Cross-Language Mappings

Linked.Archi LeanIX Cross-Language Mappings: Overview back to ToC

This ontology has the following classes and properties.

Annotation Properties

• close match
• creator
• description
• issued
• license
• modified
• preferred namespace prefix
• preferred namespace uri
• related match
• source
• title

Linked.Archi LeanIX Cross-Language Mappings: Description back to ToC

Cross-language SKOS mappings between SAP LeanIX Meta Model v4 fact sheet types and relations and ArchiMate modeling language concepts, for both ArchiMate 3.2 and ArchiMate 4.0. These mappings are editorial. SAP LeanIX publishes guidance on how its meta model relates to enterprise architecture practice, but no normative element-level correspondence to ArchiMate, and the ArchiMate specification does not mention LeanIX. The assertions here express semantic proximity based on the fact sheet definitions in the LeanIX documentation and the concept definitions in the ArchiMate specifications. LeanIX is a portfolio tool: a fact sheet is the unit of inventory, ownership and lifecycle, and its relations record support and dependency rather than detailed behaviour. Where a fact sheet type and an ArchiMate concept describe the same kind of thing at the same grain — Business Capability and Capability, Value Stream and Value Stream, Data Object and Data Object — the mapping is skos:closeMatch; exactMatch is avoided throughout because each fact sheet type carries portfolio semantics (lifecycle, subscriptions, completion) that the ArchiMate concept does not. Where LeanIX collapses several ArchiMate concepts into one type (Interface, IT Component) the mappings are skos:relatedMatch and fan out. Relation mappings carry a caveat on direction. LeanIX relations are stored on the fact sheet that owns them (an application requires an IT component; an IT component is part of a platform), which often runs opposite to the ArchiMate reading (the IT component serves the application; the platform aggregates the component). The SKOS assertions relate the relationship types only; a query that translates instances must reverse the direction where the comment says so. These are type-level statements. Instance-level correspondence is asserted in the export's Linked.Archi fact sheet index, against a shared id namespace. Not mapped, deliberately: lmm:FactSheet (abstract), lmm:BusinessContext (abstract; its subtypes are mapped), and subscriptions, tags, status and lifecycle phases, which are portfolio metadata rather than architecture.

Cross-reference for Linked.Archi LeanIX Cross-Language Mappings classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi LeanIX Cross-Language Mappings.

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.